Systems and methods for managing configurations of multiple displays of a vehicle

ABSTRACT

Disclosed are methods, systems, and non-transitory computer-readable medium for managing configurations of multiple vehicle displays. For instance, a method may include: obtaining a configurable file for an electronic checklist; generating a graphical user interface (GUI) based on the configurable file; displaying the GUI on one of the multiple vehicle displays; receiving a user input on the GUI; and performing a window configuration setting process based on the user input. The method may also include: in response to the user input being a first user input type in a region associated with a context menu indicator: obtaining a window configuration function and a phase of flight variable; generating a context menu based on the window configuration function and the POF variable; and displaying the context menu on the GUI.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims the benefit of priority to U.S. ProvisionalApplication No. 62/779,990, filed Dec. 14, 2018, which is incorporatedherein by reference in its entirety.

TECHNICAL FIELD

Various embodiments of the present disclosure relate generally tosystems and methods for managing configurations of multiple displays ofvehicles and, more particularly, to systems and methods for managingconfigurations of multiple vehicle displays using a graphic userinterface (GUI).

BACKGROUND

Modern vehicles (e.g., aircraft) may segment multiple displays intowindows of predetermined size and information content suitable for aparticular task. Specifically, managing windows may be a means ofmanaging information. Managing information may be one of the mostimportant and difficult tasks that users of vehicles (e.g., flightcrews) encounter. The windows may be thought of as “buckets” to hold andorganize information. Therefore, this windowing scheme may providesubstantial flexibility and versatility; however, it also may addadditional cognitive and physical workload on the user to manage thewindows.

Furthermore, while some predetermined window management schemes exist insome aircraft, The predetermined window management schemes may be nestedin menu layering. For instance, the user may need to make five to ten,or even more inputs to traverse menu(s) or link(s) to fully reconfigureall or some of the windows or to finally arrive at the predeterminedwindow management schemes display. Therefore, the user may beinefficient in traversing the menu(s) or link(s) and be inefficient inmaking the changes to reconfigure all or some of the windows.

Moreover, the traversal of menu(s) or link(s) may require the user todivert from checklist items to reconfigure all or some of the windows,therefore reducing efficiency and/or increasing the time to completechecklist items.

The present disclosure is directed to overcoming one or more of theseabove-referenced challenges.

SUMMARY OF THE DISCLOSURE

According to certain aspects of the disclosure, systems and methods aredisclosed for systems and methods for managing configurations ofmultiple vehicle displays.

For instance, a method may include obtaining a configurable file for anelectronic checklist; generating a graphical user interface (GUI) basedon the configurable file; displaying the GUI on one of the multiplevehicle displays; receiving a user input on the GUI; and performing awindow configuration setting process based on the user input.

A system may include a memory storing instructions; and a processorexecuting the instructions to perform a process. The process may includeobtaining a configurable file for an electronic checklist; generating agraphical user interface (GUI) based on the configurable file;displaying the GUI on one of the multiple vehicle displays; receiving auser input on the GUI; and performing a window configuration settingprocess based on the user input.

A non-transitory computer-readable medium may store instructions that,when executed by a processor, cause the processor to perform a method.The method may include: obtaining a configurable file for an electronicchecklist; generating a graphical user interface (GUI) based on theconfigurable file; displaying the GUI on one of the multiple vehicledisplays; receiving a user input on the GUI; and performing a windowconfiguration setting process based on the user input.

Additional objects and advantages of the disclosed embodiments will beset forth in part in the description that follows, and in part will beapparent from the description, or may be learned by practice of thedisclosed embodiments.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the disclosed embodiments, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate various exemplary embodiments andtogether with the description, serve to explain the principles of thedisclosed embodiments.

FIG. 1 depicts an exemplary system environment, according to one or moreembodiments.

FIG. 2 depicts a GUI on a touch screen for managing configurations ofmultiple vehicle displays, according to one or more embodiments.

FIG. 3 depicts a GUI on a touch screen for managing configurations ofmultiple vehicle displays, according to one or more embodiments.

FIG. 4 depicts a flow chart of an exemplary method for managingconfigurations of multiple vehicle displays, according to one or moreembodiments.

FIG. 5 depicts an example system that may execute techniques presentedherein.

DETAILED DESCRIPTION OF EMBODIMENTS

Various embodiments of the present disclosure relate generally tosystems and methods for managing configurations of multiple vehicledisplays.

The terminology used below may be interpreted in its broadest reasonablemanner, even though it is being used in conjunction with a detaileddescription of certain specific examples of the present disclosure.Indeed, certain terms may even be emphasized below; however, anyterminology intended to be interpreted in any restricted manner will beovertly and specifically defined as such in this Detailed Descriptionsection. Both the foregoing general description and the followingdetailed description are exemplary and explanatory only and are notrestrictive of the features, as claimed.

As used herein, the terms “comprises,” “comprising,” “having,”including,” or other variations thereof, are intended to cover anon-exclusive inclusion such that a process, method, article, orapparatus that comprises a list of elements does not include only thoseelements, but may include other elements not expressly listed orinherent to such a process, method, article, or apparatus. In thisdisclosure, relative terms, such as, for example, “about,”“substantially,” “generally,” and “approximately” are used to indicate apossible variation of ±10% in a stated value. The term “exemplary” isused in the sense of “example” rather than “ideal.” As used herein, thesingular forms “a,” “an,” and “the” include plural reference unless thecontext dictates otherwise.

While this disclosure describes the systems and methods with referenceto aircraft, it should be appreciated that the present systems andmethods are applicable to managing display screens of vehicles,including those of drones, automobiles, ships, or any other autonomousand/or Internet-connected vehicle.

In general, the present disclosure is directed to systems and methodsfor managing configurations of multiple displays. Specifically, asdiscussed more fully below, the present disclosure may enable users ofvehicles to quickly and easily manage window layout. Moreover, the usersmay be able to manage window layout quickly and easily in the normalcourse of cockpit activities (e.g., while performing checklist itemtasks).

For instance, in one aspect of the disclosure, the user may managewindow layout while interacting with checklists to set up set up anappropriate phase of flight (POF) window configuration withoutdisrupting checklist item tasks. Specifically, the user may input afirst user input to prompt a context menu that may display one or morerelevant POF window configurations. Therefore, the user may avoidtransversal of menu(s) or link(s) to reconfigure all or some of thewindows, and thereby efficiently reconfigure the windows withoutdiverting from the checklist item tasks.

As shown in FIG. 1, an exemplary system environment is depicted,according to one or more embodiments. Specifically, FIG. 1 is afragmentary perspective view illustrating the inside of an exemplaryaircraft cockpit 20. Although the context of the following discussion iswith respect to GUIs of touch screen displays used in aircraft, itshould be understood that the teachings herein pertain to touch screendisplays used in any type of vehicle including, but not limited to, landbased vehicles such as automobiles and trains as well as watercraft andspacecraft. Additionally, the teachings herein are not limited tovehicle applications. Rather, the teachings herein may also be usedtogether with touch screen displays that are employed in stationaryapplications such as information kiosks and automatic teller machines aswell as with touch screen displays that are hand held or otherwise notmounted to a surface.

Aircraft cockpit 20 includes an instrument panel 22 positioned to beaccessible from a pilot seat 24 and a copilot seat 26. Instrument panel22 includes various front displays 28 and various control features suchas buttons 30, switches 32, and throttle controls 34. Also mounted oninstrument panel 22 is a control touch screen display 36. Moreover, thefront displays 28 may also be a touch screen displays.

One of the front displays 28 or the control touch screen display 36 maybe configured to operate as a checklist manager (hereinafter referred toas “touch screen”). Specifically, a processor may execute a checklistcontrol program (comprised of instructions executable by the processor)that causes the touch screen to display a checklist control display. Forinstance, the checklist control display may include one or more GUIs asdisclosed herein (or variations thereof), such as GUI 200 and GUI 300(as depicted in FIGS. 2 and 3, respectively). The GUI 200 may depict anelectronic checklist on the touch screen. The GUI 300 may depict theelectronic checklist on the touch screen in response to the first userinput.

The processor may cause the touch screen to display the checklistcontrol display by generating images and transmitting the images to thetouch screen to be displayed. Alternatively, the processor may generateinstructions and information and transmit the instructions andinformation to a graphics processing unit (GPU). The GPU may generatethe images to be displayed on the touch screen. The checklist controlprogram may be stored in a memory. The memory may be connected to theprocessor so that the processor may receive stored instructions or data,and the processor may process the instructions, stored data, andreceived information in accordance with the checklist control program.The memory and the processor may be connected to the touch screen eitherdirectly or indirectly. Collectively the memory, the processor, and thetouch screen may be referred to as a “system.”

For instance, the checklist control program may control theconfiguration of the front displays 28 and/or the control touch screendisplay 36 (collectively “configured state”). The checklist controlprogram may store the configured state in the memory. The checklistcontrol program may control the configuration of the front displays 28and/or the control touch screen display 36 based on user inputs to thesystem. Specifically, the checklist control program may display thechecklist control display to depict the electronic checklist, andreceive user inputs to view and/or change to the configured state of thefront displays 28 and/or the control touch screen display 36.

User inputs may be the first user input, or any other type of user inputdescribed herein. Generally, the user input may be a touch interactionwith the touch screen (e.g., capacitive, resistive, and/or opticalsensing), a user input on a keyboard, a mouse, a scroll wheel, or anyother system-defined manner of selecting and interacting with thesystem. The processor may receive the user inputs and perform specificactions based on the user inputs, as discussed herein.

In one aspect of the disclosure, user interactions with the frontdisplays 28 and/or touch screen display 36 may include a first userinput. In one embodiment, the first user input may be a short touch on aregion associated with an icon or a long touch on the region associatedwith an icon. The short touch may be any touch on the region for morethan a minimum amount up to a configurable threshold period of time(e.g., less than one second). The long touch may be any touch for morethan a configurable period of time (e.g., more than two seconds) up to amaximum period of time. The period of time for the short touch and thelong touch may be the same or the period of time for the short touch maybe less than the period of time for the long touch. Other user inputsmay be one of or a combination of: a tap (e.g., a touch on a region ofan icon for less than a minimum period of time), a swipe (e.g., a touchon a region of an icon that moves/drags/remains in contact with thetouch screen interface from a starting position in the region to anending position in the region or out of the region by a thresholddistance), or multi-finger inputs (e.g., two or more discernable touchpoints in a region). Generally, in another aspect of the disclosure, thefirst user input may be one of: a short touch, a long touch, a tap, aswipe in a direction, or a multi-finger input (referred to as a “firstinput type”).

FIG. 2 depicts a GUI 200 on a touch screen for managing configurationsof multiple vehicle displays on a vehicle, according to one or moreembodiments. For example, GUI 200 may be displayed on front displays 28and/or touch screen display 36 of an instrument panel 22 of an aircraftcockpit 20. In one embodiment, GUI 200 may display any type of vehiclechecklist control display, such as an aviation checklist, such asline-up checklist 205, as depicted.

Generally, the checklist control display of GUI 200 may include any typeof electronic checklist. The electronic checklist may include aconfigurable file to generate and display checklists. The configurablefile may store the checklists in association with all checklist itemsassociated with the checklists and various indications, values,information, etc. for the checklist items. Moreover, the electronicchecklist may also include an active mission file. The active missionfile may store all user or system inputs in association with thechecklists and the checklist items. The processor may obtain theconfigurable file and the active mission file to generate the checklistcontrol display for the currently active checklist.

A checklist of the electronic checklist may include a checklist title205, an underline bar 210, and/or one or more checklist items 215. Thechecklist may also include a back button and/or a reset button.

The checklist title 205 of the currently displayed checklist of theelectronic checklist may depict a text-string. The text-string may becomposed of alphanumeric symbols that convey information to the usersabout the phase of flight and/or emergency situations associated withthe checklist. The checklist title 205 may be located in a header of theGUI, and it may remain in the header of the GUI even if the window ofthe GUI scrolls down or up.

The underline bar 210 may indicate that the associated icon (e.g., thechecklist title 205 of the currently displayed checklist of theelectronic checklist) has a context menu accessible by the first userinput. Generally, the underline bar 210 (or context menu indicator) maybe associated (and displayed) with any graphical element (e.g., icon,text, task, header, title, etc.) to indicate that the graphical elementhas a context menu accessible by the first user input. The context menuand the first user input are discussed below with respect to FIG. 3.

The one or more checklist items 215 may be items with information abouttasks associated with the currently displayed checklist of theelectronic checklist. The one or more checklist items 215 may beselected or interacted with based on user inputs. For instance, the usermay indicate that some of the checklist items are complete by touchinputs to regions of the touch screen associated with the checklistitems 215. The checklist control program may determine the currentlyactive checklist is accomplished/finished by a user input. For instance,by a user input indicating last check list item of the checklist items215 is finished/accomplished (either all items are finished/accomplishedor all required items if some are optional are finished/accomplished) orby a user input indicating to move to a next checklist of the electronicchecklist.

The back button and/or the reset button may control the electronicchecklist functionality. Specifically, the reset button may be selectedby the user by a user input, and the touch screen may receive that userinput. The touch screen may transmit the user input to the processor,and the processor may refresh and/or set the currently active checklistto default settings. The back button may be selected by the user by auser input, and the touch screen may receive that user input. The touchscreen may transmit the user input to the processor, and the processormay undo the most recent user interface associated with the checklistand/or undo a change in window configuration, and/or the processor maymove to a different checklist of the electronic checklist.

FIG. 3 depicts a GUI on a touch screen for managing configurations ofmultiple vehicle displays on a vehicle, according to one or moreembodiments. Generally, any item having the underline bar 210 (e.g., anychecklist title 205 of the checklists of the electronic checklist) maybe interacted with as discussed below with respect checklist title 205.Specifically, FIG. 3 may depict a GUI as a part of a windowconfiguration setting process. The window configuration setting processmay include: receiving a user input; determining whether the user inputis in a region associated with a graphical element that is associatedwith a context menu; and in response to determining the user input is ina region associated with the graphical element, displaying a contextmenu (“menu”) for selecting a window configuration of the displays ofthe vehicle. After displaying the menu, the window configuration settingprocess may receive another user input to select a window configurationof the displays of the vehicle. For instance, the window configurationsetting process may determine whether the another user input is in aregion associated with one of one or more window configuration options;and if so, configure the displays of the vehicle in accordance with theone of one or more window configuration options.

FIG. 3 depicts an exemplary GUI 300 of the checklist manager, forinstance as in FIG. 2, but after/in response to receiving a first userinput. Therefore, GUI 300 may be the same as the GUI 200, however GUI300 may also include a menu 305. The menu 305 may be the context menudiscussed above associated with the underline bar 230. For instance,each of the checklist titles 205 of the electronic checklist mayindicate the presence or availability of a different type of contextmenu. For instance, as depicted in FIG. 3, the line-up checklist may nothave the same context menu as a context menu associated with a taxichecklist. Alternatively, the same context menu may be displayed by thechecklist control program in response to the first user input on achecklist title 205.

For instance, as depicted in FIG. 3, the menu 305 may depict the contextmenu for the line-up checklist. The menu 305 may display one or moredifferent window configuration options (or a plurality of windowconfiguration options) and provide the user with an interface to make aselection of one or more window configuration options. For instance, themenu 305 may include a first window configuration 305A, a second windowconfiguration 305B, and/or a third window configuration 305C. To closethe menu 305, the user may input a user input anywhere else on thescreen. The menu 305 may be displayed below the checklist title 205and/or in a same horizontal (from a left or right edge of the GUI)section or general area of the GUI as the checklist title 205 associatedwith the menu 305. Furthermore, the menu 305 may have an indicatorcarrot that extends from the menu 305 to the checklist title 205associated with the menu 305.

In general, first window configuration 305A, second window configuration305B, third window configuration 305C, and any other windowconfigurations may be displayed in a sequence corresponding to eitherthe phase of flight, checklist sequence, a priority sequence, afrequency-of-use sequence, or any other desired sequence. For example,in one embodiment, the first window configuration 305A may correspond toa window configuration for the present checklist and/or current phase offlight. The second window configuration 305B may correspond to a windowconfiguration for the most recent checklist and/or most recent phase offlight, or a window configuration for a next checklist and/or next phaseof flight. The third window configuration 305C may correspond to adefault or standard window configuration for any checklist and/or phaseof flight (e.g., a “generic” window configuration).

The first window configuration 305A and the second window configuration305B may include information (e.g., text) that indicates what type ofwindow configuration will be implemented. For instance, the informationmay include a text-string that states the window configuration optionwill configure the display units (DUs) for a POF name or checklist name.For instance, the POF name may be one of: (1) Cockpit Preparation; (2)Before Start; (3) After start; (4) Line-Up; (5) Takeoff; (6) AfterTakeoff; (7) Approach; (8) Before Landing; (9) At Ramp; and/or (10)Securing The Aircraft. For instance, the checklist name may be one of:(1) Cockpit Preparation Checklist; (2) Before Start Checklist; (3) Afterstart Checklist; (4) Line-Up Checklist; (5) Takeoff Checklist; (6) AfterTakeoff Checklist; (7) Approach Checklist; (8) Before Landing Checklist;(9) At Ramp Checklist; and/or (10) Securing The Aircraft Checklist. Theabove list of checklists names or POF names may correspond to originalequipment manufacturer (OEM) definitions, which may be aligned with crewinformation and task organization, and do not necessarily align with anyInternational Civil Aviation Organization's (ICAO) definitions.

The third window configuration 305C may include information (e.g., text)that indicates what type of window configuration will be implemented.For instance, the information may include a text-string that states thewindow configuration option will configure the display units (DUs) forStandard or Default.

Alternatively, or in addition, the menu 305 may include more than threewindow configuration options. For instance, the menu 305 may include thethree discussed above along with a link to all pre-defined windowconfiguration or at the top of a list of all the pre-defined windowconfigurations. Furthermore, the menu 305 may include user definedwindow configurations that may define the configuration of the windowsand associate the configuration with a user-defined name, which may bedisplayed with the user defined window configuration option. Moreover,the checklist control program may store the last window configurationand also provide a last window configuration option to the menu 305, sothat the user may quickly recover from an inadvertent selection andactivation.

Furthermore, the electronic checklist may also include a windowconfiguration file and/or window configuration rules (or windowconfiguration function). The window configuration file and/or the windowconfiguration rules may store all of the pre-defined windowconfigurations and/or user-defined window configurations for the frontdisplays 28 and/or the control touch screen display 36. For instance, ataxi window configuration may control one or more of the front displaysto display one or more a map of a current airport and an aircraft'slocation the map, a map of the runways and the aircraft's location themap, traffic for the airport (on ground and/or in the air), and/orweather for the airport.

The window configuration function may associate a POF variable of thesystem to the currently active checklist and/or POF of the vehicle (asindicated by a user input or by another system of the vehicle).Specifically, the POF variable may correspond to each of the abovediscussed POF names, the above discussed checklist names, or to some orall of the checklists of the electronic checklist. The POF variable maybe used to determine the current phase of flight for the aircraft. Thismay overcome problems with determining POF flight based on, e.g., flightpath or aircraft dynamics in flight or during ground operations.

The window configuration function may define which window configurations(of all pre-define window configurations) are displayed for the firstwindow configuration 305A and the second window configuration 305B,based on the POF variable. For instance, if the POF variable indicatesthe current POF is takeoff, then the first window configuration 305A maycorrespond to a takeoff window configuration and the second windowconfiguration 305B may correspond to a taxi window configuration (as thetaxi POF preceded the takeoff POF).

The pre-defined window configurations may be set by the OEM or may beconfigurable so that an aircraft organization (e.g., airline) may setthe pre-defined window configurations. The association between the POFvariable and which window configurations (of all pre-define windowconfigurations) are displayed for the first window configuration 305Aand the second window configuration 305B may be set by the OEM or may beconfigurable so that the aircraft organization may set the association.

An example reconfiguration process may include: when/in response to thefirst user input in a region associated with an underline bar 210 (e.g.,any checklist title 205 of the checklists of the electronic checklist,such as in FIG. 2), the touch screen may receive the first user input,and transmit a first input message to the processor indicating the firstuser input and the underline bar 210 region. The processor may, inresponse to the first user input and the region, cause a menu to bedisplayed that includes one or more window configuration options (see,e.g., FIG. 3). The processor may determine which window configurationoptions to display based on a stored POF variable and a windowconfiguration function.

The user may input a second user input to the touch screen. The touchscreen may receive the second user input, and transmit a second inputmessage to the processor indicating the second user input and a regionassociated with one of the one or more window configuration options. Theprocessor may, in response to the second user input and the regionassociated with one of the one or more window configuration options,determine which one of the one of the one or more window configurationoptions was selected. The processor may, based on the selected windowconfiguration option, configure the front displays 28 or the controltouch screen display 36 in accordance with a window configurationcorresponding to the selected window configuration option. The processormay then close the menu. For instance, the processor may change theconfigured state in accordance with the window configurationcorresponding to the selected window configuration option.

Moreover, the first window configuration option of the windowconfiguration options may be auto-selected in response to the display ofthe menu. The processor may cause the first window configuration optionto be highlighted in a different color from the other options (so thatthe user may be made aware of the auto-selection). The user may selectthe auto-selection without touch interacting with the touch screen by(1) waiting a predefined period of time (e.g., more than five seconds)or (2) by pressing a button (e.g., enter button on a keyboard, a mouseclick on a mouse, or an enter or press on Cursor Control Device (CCD)).

FIG. 4 depicts a flow chart for managing configurations of multipledisplays, according to one or more embodiments. The flowchart 400 maydepict a method. The method may include, by a system with a processor,memory, and touch screen: determine whether the touch screen hasreceived a first user input (block 402). If no first user input isreceived, the method may continue to wait until the first user input isreceived (block 402: No).

If a first user input is received (block 402: Yes), the method mayproceed to determine whether the first user input is in a regionassociated with a context menu (block 404). If not (block 404: No), themethod may proceed to perform a second action based on the first userinput (block 406). Then, the method may proceed to wait for a first userinput again (block 402).

If the first user input is in the region associated with the contextmenu (block 404: Yes), the method may proceed to determine whether thefirst user input is a first user input type (block 408).

If not (block 408: No), the method may proceed to perform a secondaction based on the first user input (block 406). Then, the method mayproceed to wait for a first user input again (block 402).

If the first user input was a first user input type (block 408: Yes),the method may proceed to display menu (block 410). The menu maycorrespond to a checklist title 204, discussed above. The menu maydisplay one or more window configuration options.

The method may proceed to determine whether a second user input isreceived (block 412). If not (block 412: No), the method may proceed towait until the second user input is received.

If the second user input is received (block 412: Yes), the method mayproceed to perform a first action based on the second user input (block414). Then, the method may proceed to wait for a first user input again(block 402).

The first action may include: (1) based on the touch screen receivingthe second user input and transmitting a second input message to theprocessor indicating the second user input and a region associated withone of the one or more window configuration options, determine which oneof the one of the one or more window configuration options was selected;(2) based on the selected window configuration option, configure thefront displays 28 or the control touch screen display 36 in accordancewith a window configuration corresponding to the selected windowconfiguration option; and (3) close the menu.

The second action may be some other interaction with the checklist ofthe electronic checklist (e.g., inputs to the one or more checklistitems 215).

In another aspect of the disclosure, the checklist control program maydisplay an underline bar 210 in association with an icon. In response tothe first user input on a region associated with the underline bar 210,a menu like the menu 305 discussed above may be displayed. The icon maynot be the checklist title 205, but instead an icon that links to one ormore different window configuration options, like the first windowconfiguration 305A, the second window configuration 305B, and/or thethird window configuration 305C, discussed above. In this manner, thechecklist control program may provide quick access to re-configure thewindows, even when not directly interacting with a checklist that has achecklist title 205 that has an underline bar 210.

In another aspect of the disclosure, the checklist control program maydisplay an underline bar 210 in association with an icon. In response tothe first user input on a region associated with the underline bar 210,the processor may perform a speech-to-action function. Specifically, theprocessor may enable a microphone to receive audio. The microphone mayreceive the audio, convert the audio into analog or digital signals, andtransmit the analog or digital signals to the system. The processor mayreceive the analog or digital signals, process the signals usingspeech-to-text software, and determine a speech command of the audio.The processor may perform an action corresponding to the speech commandof the audio. Specifically, the processor may interpret the speechcommand of the audio to configure the front displays 28 or the controltouch screen display 36 based on the speech command naming one of thePOF names or the checklist names, as listed out above. For instance, theuser may say “configure the display units for takeoff,” and theprocessor may (1) process the audio to determine that the front displays28 or the control touch screen display 36 are to be configured fortakeoff, and (2) configure the front displays 28 or the control touchscreen display 36 based on a takeoff window configuration stored in thewindow configuration file and/or the window configuration rules.

FIG. 5 depicts an example system that may execute techniques presentedherein. FIG. 5 is a simplified functional block diagram of a computerthat may be configured to execute techniques described herein, accordingto exemplary embodiments of the present disclosure. Specifically, thecomputer (or “platform” as it may not be a single physical computerinfrastructure) may include a data communication interface 560 forpacket data communication. The platform may also include a centralprocessing unit (“CPU”) 520, in the form of one or more processors, forexecuting program instructions. The platform may include an internalcommunication bus 510, and the platform may also include a programstorage and/or a data storage for various data files to be processedand/or communicated by the platform such as ROM 530 and RAM 540,although the system 500 may receive programming and data via networkcommunications. The system 500 also may include input and output ports550 to connect with input and output devices such as keyboards, mice,touchscreens, monitors, displays, etc. Of course, the various systemfunctions may be implemented in a distributed fashion on a number ofsimilar platforms, to distribute the processing load. Alternatively, thesystems may be implemented by appropriate programming of one computerhardware platform.

The general discussion of this disclosure provides a brief, generaldescription of a suitable computing environment in which the presentdisclosure may be implemented. In one embodiment, any of the disclosedsystems, methods, and/or graphical user interfaces may be executed by orimplemented by a computing system consistent with or similar to thatdepicted and/or explained in this disclosure. Although not required,aspects of the present disclosure are described in the context ofcomputer-executable instructions, such as routines executed by a dataprocessing device, e.g., a server computer, wireless device, and/orpersonal computer. Those skilled in the relevant art will appreciatethat aspects of the present disclosure can be practiced with othercommunications, data processing, or computer system configurations,including: Internet appliances, hand-held devices (including personaldigital assistants (“PDAs”)), wearable computers, all manner of cellularor mobile phones (including Voice over IP (“VoIP”) phones), dumbterminals, media players, gaming devices, virtual reality devices,multi-processor systems, microprocessor-based or programmable consumerelectronics, set-top boxes, network PCs, mini-computers, mainframecomputers, and the like. Indeed, the terms “computer,” “server,” and thelike, are generally used interchangeably herein, and refer to any of theabove devices and systems, as well as any data processor.

Aspects of the present disclosure may be embodied in a special purposecomputer and/or data processor that is specifically programmed,configured, and/or constructed to perform one or more of thecomputer-executable instructions explained in detail herein. Whileaspects of the present disclosure, such as certain functions, aredescribed as being performed exclusively on a single device, the presentdisclosure may also be practiced in distributed environments wherefunctions or modules are shared among disparate processing devices,which are linked through a communications network, such as a Local AreaNetwork (“LAN”), Wide Area Network (“WAN”), and/or the Internet.Similarly, techniques presented herein as involving multiple devices maybe implemented in a single device. In a distributed computingenvironment, program modules may be located in both local and/or remotememory storage devices.

Aspects of the present disclosure may be stored and/or distributed onnon-transitory computer-readable media, including magnetically oroptically readable computer discs, hard-wired or preprogrammed chips(e.g., EEPROM semiconductor chips), nanotechnology memory, biologicalmemory, or other data storage media. Alternatively, computer implementedinstructions, data structures, screen displays, and other data underaspects of the present disclosure may be distributed over the Internetand/or over other networks (including wireless networks), on apropagated signal on a propagation medium (e.g., an electromagneticwave(s), a sound wave, etc.) over a period of time, and/or they may beprovided on any analog or digital network (packet switched, circuitswitched, or other scheme).

Program aspects of the technology may be thought of as “products” or“articles of manufacture” typically in the form of executable codeand/or associated data that is carried on or embodied in a type ofmachine-readable medium. “Storage” type media include any or all of thetangible memory of the computers, processors or the like, or associatedmodules thereof, such as various semiconductor memories, tape drives,disk drives and the like, which may provide non-transitory storage atany time for the software programming. All or portions of the softwaremay at times be communicated through the Internet or various othertelecommunication networks. Such communications, for example, may enableloading of the software from one computer or processor into another, forexample, from a management server or host computer of the mobilecommunication network into the computer platform of a server and/or froma server to the mobile device. Thus, another type of media that may bearthe software elements includes optical, electrical and electromagneticwaves, such as used across physical interfaces between local devices,through wired and optical landline networks and over various air-links.The physical elements that carry such waves, such as wired or wirelesslinks, optical links, or the like, also may be considered as mediabearing the software. As used herein, unless restricted tonon-transitory, tangible “storage” media, terms such as computer ormachine “readable medium” refer to any medium that participates inproviding instructions to a processor for execution.

Other embodiments of the disclosure will be apparent to those skilled inthe art from consideration of the specification and practice of theinvention disclosed herein. It is intended that the specification andexamples be considered as exemplary only, with a true scope and spiritof the invention being indicated by the following claims.

What is claimed is:
 1. A method for managing configurations of multiplevehicle displays, comprising: obtaining a configurable file for anelectronic checklist; generating a graphical user interface (GUI) basedon the configurable file; displaying the GUI on one of the multiplevehicle displays; receiving a user input on the GUI; and performing awindow configuration setting process based on the user input.
 2. Themethod of claim 1, wherein the GUI includes a plurality of tasks of theelectronic checklist and at least one graphical element associated witha context menu indicator.
 3. The method of claim 2, wherein before theperforming the window configuration setting process, the method furthercomprises: determining whether an input region of the user input is in aregion associated with the at least one graphical element; and inresponse to determining the input region of the user input is in theregion associated with the at least one graphical element, determiningwhether the user input is a first user input type; in response todetermining the user input is the first user input type, performing thewindow configuration setting process based on the user input and the atleast one graphical element.
 4. The method of claim 3, wherein theperforming the window configuration setting process based on the userinput and the at least one graphical element includes: obtaining awindow configuration function and a phase of flight variable; generatinga context menu based on the window configuration function and the POFvariable; and displaying the context menu on the GUI.
 5. The method ofclaim 4, wherein the context menu includes a plurality of windowconfiguration options.
 6. The method of claim 5, further comprising:receiving a second user input; determining whether a second input regionof the second user input is in a region associated with one of theplurality of window configuration options; and in response determiningthe second input region of the second user input is in the regionassociated with one of the plurality of window configuration options,configuring the multiple vehicle displays in accordance with the one ofthe plurality of window configuration options.
 7. The method of claim 5,wherein a first window configuration option of the plurality of windowconfiguration options corresponds to a present checklist of theelectronic checklist and/or current phase of flight as indicated by thePOF variable, and a second window configuration option of the pluralityof window configuration options corresponds to either: a most recentchecklist of the electronic checklist and/or a most recent phase offlight as indicated by the POF variable, or a next checklist of theelectronic checklist and/or a next phase of flight as indicated by thePOF variable.
 8. A system for managing configurations of multiplevehicle displays, the system comprising: a memory storing instructions;and a processor executing the instructions to perform a processincluding: obtaining a configurable file for an electronic checklist;generating a graphical user interface (GUI) based on the configurablefile; displaying the GUI on one of the multiple vehicle displays;receiving a user input on the GUI; and performing a window configurationsetting process based on the user input.
 9. The system of claim 8,wherein the GUI includes a plurality of tasks of the electronicchecklist and at least one graphical element associated with a contextmenu indicator.
 10. The system of claim 9, wherein before the performingthe window configuration setting process, the process further includes:determining whether an input region of the user input is in a regionassociated with the at least one graphical element; and in response todetermining the input region of the user input is in the regionassociated with the at least one graphical element, determining whetherthe user input is a first user input type; in response to determiningthe user input is the first user input type, performing the windowconfiguration setting process based on the user input and the at leastone graphical element.
 11. The system of claim 10, wherein theperforming the window configuration setting process based on the userinput and the at least one graphical element includes: obtaining awindow configuration function and a phase of flight variable; generatinga context menu based on the window configuration function and the POFvariable; and displaying the context menu on the GUI.
 12. The system ofclaim 11, wherein the context menu includes a plurality of windowconfiguration options.
 13. The system of claim 12, the process furtherincludes: receiving a second user input; determining whether a secondinput region of the second user input is in a region associated with oneof the plurality of window configuration options; and in responsedetermining the second input region of the second user input is in theregion associated with one of the plurality of window configurationoptions, configuring the multiple vehicle displays in accordance withthe one of the plurality of window configuration options.
 14. The systemof claim 13, wherein a first window configuration option of theplurality of window configuration options corresponds to a presentchecklist of the electronic checklist and/or current phase of flight asindicated by the POF variable, and a second window configuration optionof the plurality of window configuration options corresponds to either:a most recent checklist of the electronic checklist and/or a most recentphase of flight as indicated by the POF variable, or a next checklist ofthe electronic checklist and/or a next phase of flight as indicated bythe POF variable.
 15. A non-transitory computer-readable medium storinginstructions that, when executed by a processor, cause the processor toperform a method for managing configurations of multiple vehicledisplays, the method comprising: obtaining a configurable file for anelectronic checklist; generating a graphical user interface (GUI) basedon the configurable file; displaying the GUI on one of the multiplevehicle displays; receiving a user input on the GUI; and performing awindow configuration setting process based on the user input.
 16. Thenon-transitory computer-readable medium of claim 15, wherein the GUIincludes a plurality of tasks of the electronic checklist and at leastone graphical element associated with a context menu indicator.
 17. Thenon-transitory computer-readable medium of claim 16, wherein before theperforming the window configuration setting process, the method furthercomprises: determining whether an input region of the user input is in aregion associated with the at least one graphical element; and inresponse to determining the input region of the user input is in theregion associated with the at least one graphical element, determiningwhether the user input is a first user input type; in response todetermining the user input is the first user input type, performing thewindow configuration setting process based on the user input and the atleast one graphical element.
 18. The non-transitory computer-readablemedium of claim 17, wherein the performing the window configurationsetting process based on the user input and the at least one graphicalelement includes: obtaining a window configuration function and a phaseof flight variable; generating a context menu based on the windowconfiguration function and the POF variable; and displaying the contextmenu on the GUI.
 19. The non-transitory computer-readable medium ofclaim 18, wherein the context menu includes a plurality of windowconfiguration options.
 20. The non-transitory computer-readable mediumof claim 15, wherein the method further comprises: receiving a seconduser input; determining whether a second input region of the second userinput is in a region associated with one of the plurality of windowconfiguration options; and in response determining the second inputregion of the second user input is in the region associated with one ofthe plurality of window configuration options, configuring the multiplevehicle displays in accordance with the one of the plurality of windowconfiguration options.